System and method for dynamic  feature selection based on latency discovery

ABSTRACT

Aspects of the subject disclosure include, for example, identifying a primary serving cell and a secondary serving cell, wherein the primary serving cell facilitates one of attachment, re-attachment or mobility, or any combination thereof, of a mobile device in association with coordination of a wireless service between the primary serving cell, the secondary serving cell and the mobile device. A latency value associated with a message exchange is determined between the primary and secondary serving cells via a messaging interface, and compared to latency requirements, which correspond to a group of mobile service features. A mobile service feature of the group is associated with the wireless service based on the comparison. The wireless service includes a coordinated exchange of wireless signals between the primary serving cell and the mobile device and between the secondary serving cell and the mobile device based on the mobile service feature. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/170,784, filed Jun. 1, 2016. All sections of theaforementioned application are incorporated herein by reference in theirentirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a system and method for dynamicfeature selection based on latency discovery.

BACKGROUND

In order to support continued growth of mobile traffic, the 3^(rd)Generation Partnership Protocol (3GPP) has introduced advanced featuresto its Long Term Evolution (LTE) architecture, generally referred to asLTE-Advanced (LTE-A). In particular, implementation of the advancedfeatures is expected to enhance network throughput and/or mobilityrobustness. Such advanced features can be provided in association withHeterogeneous Network (HetNet) to improve coverage, capacity and/orperformance of a mobile network.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a portion of a mobilecellular network that implements feature selection based on latencymeasurements;

FIG. 2A depicts an illustrative embodiment of a schematic diagram of aportion of a mobile cellular system that implements feature selectionbased on latency measurements;

FIG. 2B depicts an illustrative embodiment of an X2 message exchange ofa latency measurement;

FIG. 3 depicts an illustrative embodiment of an embodiment of a processused by the systems of FIGS. 1 and 2;

FIG. 4 depicts an illustrative embodiment of another embodiment ofprocess used by the systems of FIGS. 1 and 2;

FIG. 5 depicts an illustrative embodiment of communication systems thatprovide media services to mobile devices using the systems of FIGS. 1and/or 2 and according to the processes of FIGS. 3 and/or 4;

FIG. 6 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1-2 and 5;

FIG. 7 depicts an illustrative embodiment of a communication device; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for determining a latency of an interface between cells of amobile cellular network and selecting features of a group of mobilefeatures that provide a common wireless service to a mobile device thatis coordinated among multiple cells, e.g., a primary serving cell and asecondary serving cell. In a 3GPP LTE architecture, the interfacebetween cells includes an “X2” interface, and the group of mobilefeatures includes, without limitation, coordinated multipoint (CoMP),carrier aggregation (CA) and dual connectivity (DC). Other feature caninclude non-real time features, such as an exchange of load information.A latency of the X2 interface can be determined by a message exchangedbetween the primary and secondary serving eNBs, e.g., by an extended X2Access Protocol (AP) according to the techniques disclosed herein. Afeature set can be determined, e.g., from among the CoMP, CA, DC andother features, based on the latency. Other embodiments are described inthe subject disclosure.

One or more aspects of the subject disclosure include a system,including a processing system including a processor and a memory thatstores executable instructions. The instructions, when executed by theprocessing system, facilitate performance of operations, includingidentifying a primary serving cell and a secondary serving cell of amobile cellular network, wherein the primary serving cell facilitatesone of attachment of a mobile device to the mobile cellular network,re-attachment of the mobile device to the mobile cellular network,mobility of the mobile device between the primary serving cell andanother cell of the mobile cellular network, or any combination thereofin association with coordination of a wireless service between theprimary serving cell, the secondary serving cell and the mobile device.The operations further include determining a latency value associatedwith a message exchange between the primary serving cell and thesecondary serving cell via a messaging interface between the primaryserving cell and the secondary serving cell. The latency value iscompared to latency requirements corresponding to a group of mobileservice features. A mobile service feature of the group of mobileservice features is associated with the wireless service based on thecomparison. The wireless service includes a coordinated exchange ofwireless signals between the primary serving cell and the mobile deviceand between the secondary serving cell and the mobile device based onthe mobile service feature of the group of mobile service features.

One or more aspects of the subject disclosure include a process thatincludes determining, by a system comprising a processing systemincluding a processor, a first cell and a second cell of a mobilecellular network, wherein the first cell facilitates coordination of awireless service to a mobile device. The process further includesdetermining, by the processing system, a latency value associated with amessage exchange between the first cell and the second cell via amessaging interface between the first cell and the second cell. Thelatency value is compared, by the processing system, to a group oflatency requirements corresponding to a group of mobile features toobtain a comparison. A mobile feature of the group of mobile features isassociated, by the processing system, with the wireless service based onthe comparison. The wireless service includes a coordinated exchange ofwireless signals between the first cell and the mobile device andbetween the second cell and the mobile device based on the mobilefeature of the plurality of mobile features.

One or more aspects of the subject disclosure include a machine-readablestorage medium, including executable instructions that, when executed bya processing system including a processor, facilitate performance ofoperations. The operations include determining a first cell and a secondcell of a mobile cellular network, wherein the first cell and the secondcell provide a joint wireless service to a mobile device. The operationsfurther include determining a latency value associated with a messageexchange between the first cell and the second cell via a messaginginterface between the first cell and the second cell. The latency valueis compared to a group of latency requirements that correspond to agroup of mobile features. A set of mobile features of the group ofmobile features is selected based on the comparison, to obtain aselected set mobile features, wherein a mobile feature of the set ofmobile features is applied to the wireless service to obtain a jointexchange of wireless signals between the first cell and the mobiledevice and between the second cell and the mobile device based on themobile feature of the set of mobile features.

FIG. 1 depicts an illustrative embodiment of a portion of a mobilecellular network 100 that implements feature selection based on latencymeasurements. The network is based on 3GPP LTE technology and includes afirst radio base station, or eNB 102 a, that services a first macro-cell104 a that operates according to a first frequency assignment, f1. It isunderstood that a single radio station, such as the first eNB 102 a, canservice more than one cell. The cells can be arranged in anon-overlapping fashion, e.g., servicing different sectors of a servicedregion. Alternatively or in addition, the cells can be overlapping,e.g., as in servicing different frequency channels and/or frequencybands of an overlapping, e.g., the same, region. In the illustrativeexample, the fist eNB 102 a also services a second, overlappingmacro-cell 104 b, operating according to a second frequency assignment,f2.

An example UE 130 a, operating within a coverage region of the firstmacro-cell 104 a, and the overlapping second macro-cell 104 b, can beserviced by the first macro-cell 104 a, the second macro-cell 104 b, ora combination of both the first and second macro-cells 104 a, 104 b.Such combined services can include wireless services coordinated amongmultiple cells and/or wireless base stations, such as the coordinatedservices disclosed herein, e.g., CoMP, CA, and/or DC. Wireless servicescan include one or more of Voice over IP (VoIP), Short Message Service(SMS), Multimedia Messaging Service (MMS), streaming audio, streamingvideo, streaming multimedia, file transfer, web browsing sessions, andthe like. Although an interface is not illustrated in FIG. 1, it isunderstood that an interface can be provided between the radio resourceservicing the first macro-cell 104 a and the second macro-cell 104 b.The interface can operate according to a standard interface protocol,such as an X2 interface, or to any other interface, including aproprietary interface.

Any of the macro-cells 104 a, 104 b can be arranged to expand capacityof wireless services in a given geographic region. For example, amacro-network can maintain a homogenous network by deploying more macroeNBs, by adding more sectors per eNB, and/or by adding more radiosservicing more radio frequency channels and/or bands per sector. It isalso understood that frequency assignment can include a frequency band,a frequency channel within the frequency band, a grouping of suchfrequency bands and/or channels, e.g., according to an up-link anddown-link channel assignments.

Alternatively or in addition, it is understood that wireless coverage ofthe network 100 can be enhanced with a deployment of one or more,so-called, small cells. A combination of macro-cells and small cellswithin the same network is generally referred to as a heterogeneousnetwork. Scenarios and requirements for small cell enhancements, aredisclosed in, for example, “3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Scenarios andrequirements for small cell enhancements for E-UTRA and E-UTRAN”(Release 13), 3GPP TR 36.932 V13.0.0, incorporated herein by referencein its entirety. Small cells generally refer to low power nodes having atransmit power that is lower than a macro node and base station (BS)classes, such as Pico and Femto eNB. The small cells can be used inhotspot deployments in indoor and outdoor scenarios to cope withincreasing mobile traffic demands.

In the illustrative example, a second radio base station, or eNB 102 b,services a third macro-cell 104 c, according to a third frequencyassignment, f3. A first small cell 114 includes a radio base station,eNB or wireless access point 112. The small cell services a hotspotwithin the coverage of the third macro-cell 104 c, according to afrequency assignment, fx. An example UE 130 b, operating within acoverage region of the first small cell 114, can be in communicationwith the small cell access point 112, the second eNB 102 b, or both. Inat least some embodiments, a first interface 115 is provided between thefirst small cell access point 112 and the second eNB 102 b.

Likewise, a second small cell 118 includes a radio base station, orwireless access point 116. Once again, the second small cell 118services a hotspot within the coverage of the third macro-cell 104 c,according to a frequency assignment, fy. Similarly, a second interface119 is provided between the second small cell access point 116 and thesecond eNB 102 b. It is understood that one or more of the firstinterface 115, the second interface 119, or the third interface 121 canoperate according to an X2 protocol, along a back-haul and/or front-haulnetwork, according to another protocol, e.g., including a proprietaryprotocol, or any combination thereof.

In the illustrative example, a third radio base station, or eNB 102 c,services a fourth macro-cell 104 d, according to a fourth frequencyassignment, f4. A third small cell 122 includes a radio base station, orwireless access point 120. The small cell 122 services a region at leastpartially outside of the coverage area of the fourth macro-cell 104 d,according to a frequency assignment, fy. An example UE 130 c, operatingwithin a coverage region of the third small cell 122, can be incommunication with the small cell access point 1120, but not necessarilyin communication with the third eNB 102 c. In at least some embodiments,an interface 123 is provided between the third small cell access point120 and the third eNB 102 c.

Each of the eNBs 102 a, 102 b, 102 c is in communication with one ormore of the others by way of a respective X2 interface. The first andthird eNBs 102 a, 102 c are in further communication with a first EPC,including a first MME/S-GW 110 a. This connectivity includes a controlplane interface S1-C and a user plane interface S1-U, generally S1,e.g., to coordinate and/or otherwise support delivery of mobile servicesto the UEs 130 a, 130 b, 130 c. Likewise, the second and third eNBs 102b, 102 c are in further communication with a first EPC, including asecond MME/S-GW 110 b.

In addition to the wireless coverage provided to mobile equipment bymacro-cells and/or small cells, the cells are also connected to othernetwork elements by way of intermediate links. Such intermediate links,e.g., between a core network or a backbone network and small subnetworksat the edge, including the eNBs 106 and/or the small cells are commonlyreferred to as a “backhaul” portion of the network. For example, thebase stations, eNBs and/or wireless access points of the cells can beconnected to a core network, such as an Evolved Packet Core (EPC) of theexample 3GPP LTE network by such a backhaul network. In the illustrativeembodiment, only a portion of such an EPC is shown, as an MME/S-GW 110a, 110 b (generally 110). The MME/SGW 110 relates to an MME (MobilityManagement Entity) network entity and an S-GW (Serving Gateway) networkentity. It is understood that any practical EPC includes other networkelements, such as the P-GW (Packet data network Gateway) and the HSS(Home Subscriber Server).

A first cell of a wireless mobile network, sometimes referred to as aprimary or coordinating serving cell, can include a cell thatcoordinates, performs or otherwise facilitates one or more of an initialconnection establishment procedure with a UE, a connectionre-establishment procedure with the UE, and/or a handover procedure forthe UE. In this manner, the primary serving cell can be thought of as acell on which the UE is “camped.” It is understood that the primaryserving cell can participate in one or more coordinated wirelessservices with the UE, including multi-cell radio access technologies,such as CoMP, Carrier Aggregation and Dual Carrier. A second cell of thewireless network, sometimes referred to as a secondary ornon-coordinating serving cell can include any other cell thatparticipates with the primary serving cell to support coordinatedwireless services with the UE, including multi-cell radio accesstechnologies. It is understood that in at least some embodiments, thesecondary serving cell may not participate in, coordinate or otherwisefacilitate the attachment, re-attachment and/or mobility of the mobiledevice in relation to a multi-cell radio access technology that includethe primary serving cell and the secondary serving cell.

Backhaul technologies include, without limitation, LMDS (LocalMultipoint Distribution Service), WiFi, WiMAX, DSL (Digital subscriberline), including ADSL (Asynchronous DSL) and SHDSL (Symmetricalhigh-speed DSL), PDH (Plesiochronous Digital Hierarchy), SDH(Synchronous Digital Hierarchy), SONET (Synchronous Optical Network) andEthernet. A backhaul portion of a network can be referred to as an“ideal” backhaul if it provides a very high throughput and very lowlatency, such as dedicated point-to-point connection using opticalfiber, free-space optical, and the like. A backhaul portion of a networkcan also be referred to as a “non-ideal” backhaul if it typical backhaulwidely used in the market such as xDSL, microwave radio relaytransmission, terrestrial and/or satellite, and other backhauls thatinclude relaying. Backhauls can be point-to-point orpoint-to-multi-point.

Each of the eNBs 102 a, 102 b, 102 c is in communication with arespective coordination controller 106 a, 106 b, 106 c, generally 106.The coordination controller 106 facilitates delivery of wireless servicefeatures that include coordinated among several nodes, e.g., accordingto CoMP, CA and/or DC. Although the coordination controllers 106 areshown in combination with the macro-cell eNBs 102, it is understood thatin at least some embodiments, a coordination controller 106 is incommunication with one or more of the small cell wireless access points112, 116, 120.

Coordinated, or multi-node features include, without limitation, CoMP,CA and DC. In some embodiments, each eNB 102 is collocated with arespective coordination controller 106. The coordination controller 106can include a separate hardware module in communication with the eNB102. Alternatively or in addition, the coordination controller 106 canbe combined with the eNB 102, e.g., as a combined hardware module and/orsoftware module. It is also envisioned that one or more of thecoordination controllers 106 can be physically separated from the eNB102, e.g., resident at a data center, such as the EPC and/or at anywhereaccessible by the Internet, e.g., at third-party operator location. Itis also understood that a coordination controller 106 can serve morethan one of the radio base stations 102.

With Coordinated multipoint transmission and/or reception (CoMP) anumber of transmission/reception points, e.g., eNBs and/or small cellradio base stations or wireless access points, can be coordinated toprovide service to a UE. For example, data can be transmitted at thesame time in the same PRB (Physical Resource Block) from more than onetransmission point to one UE, or data can be received from onetransmission point in one sub-frame and from another transmission pointin the next sub-frame. When CoMP is used in a heterogeneous network anumber of macro-cells and small cells can be involved in datatransmission to and from one UE.

CoMP requires that the involved cells coordinate their radio frequencysignal in a highly accurate way, e.g., according to phasesynchronization and high-capacity connectivity with low latency.Coordinating features, such as CoMP, benefit from time synchronizationand in inter-cell communication. In an LTE scenario, the inter-cellcommunications can leverage respective interfaces of the LTEarchitecture, such as the X2 interface between eNBs.

Another coordinated wireless service feature is referred to as CarrierAggregation (CA). When CA is used a number of radio frequency carriers,referred to as Component Carriers (CC), are aggregated and a CA-capableUE can be allocated resources on one or more CCs. Cross-carrierscheduling is an important feature in heterogeneous networks. Usingcross-carrier scheduling it is possible to map PDCCH (Physical DownlinkControl Channels) on different CCs in the large and small cells.

With spectrum allocated for 4G networks, operators often find they havea variety of small bands that they have to piece together to provide therequired overall bandwidth needed for 4G LTE. Making these bands workseamlessly is a key element of the LTE heterogeneous network operation.

Yet another coordinated wireless service feature is referred to as DualCarrier (DC). According to DC operations, a UE can receive and/ortransmit data from and/or to multiple eNBs simultaneously, e.g.,carriers can be bundled by the network. One of the eNBs can be referredto as a Master eNB (MeNB), while one or more other eNBs can be referredto as Secondary eNBs (SeNB). Backhaul between low power nodes providingsmall cells and macro nodes may be ideal or non-ideal. Intra-eNB CA andCoMP features assume ideal backhaul in which centralized scheduling canbe implemented for efficient radio resource utilization. DC extends CA &CoMP to inter-eNB with non-ideal backhaul.

With present mobile backhaul networks, the X2 interface is typicallyconnected through a service edge router that links each radio basestations with its controller and/or S-GW. Control traffic must beexchanged with stringent delay requirements of less than about 1millisecond. Each radio needs to be supplied with precise time/phaseinformation with accuracy in the order of sub-millisecond, e.g.,microsecond. Location-based services demand even lower tolerance ofsub-microsecond, as phase differences among several radio signals can beused to calculate the location of user equipment. Such stringentrequirements can drive a change in the backhaul architecture to switchand/or rout the X2 interface closer to the radio base stations, sometimereferred to as front-haul networks. Without limitation, such front-haulnetworks can include fiber to the cell site, renting dark fiber, sharingfiber and/or the transmission system with another operator or leasebandwidth from a wholesale bandwidth provider, and the like. Withoutlimitation, interconnections between radio base stations, includingmacro-cell and/or small cell can be in communication with one or moreother macro-cells and/or small cells by way of back-haul networks,front-haul networks, or any combination thereof.

FIG. 2 depicts an illustrative embodiment of a schematic diagram of aportion of another mobile cellular system 200 that implementsconfiguration feature selection based on latency measurements. Thesystem includes a Master eNB (MeNB) 202 having a radio resource control(RRC) 204 and a coordination controller 206 a. The RRC 204 facilitatesestablishment and coordination of wireless connectivity with a mobilestation, or UE 230. The system 200 includes at least one secondary orsupporting eNB (SeNB) 202 b. The SeNB 202 b includes radio resources tosupport wireless communications with the UE 230. Although the SeNB 202 bmay include an RRC (not shown), it is not necessary for at least some ofthe coordinating features.

In the illustrative example, the UE 230 also includes a radio to supportwireless communications with the MeNB 202 a and/or the SeNB 202 b. TheUE 230 includes an RRC 232 to facilitate wireless connectivity with atleast the MeNB 202 a. The RRC 204, 232, provides a Radio ResourceControl protocol used in UMTS and LTE on the Air interface. For example,the RRC 204, 232 handles control plane signaling between the UE 230 andthe Radio Access Network (UTRAN or E-UTRAN) as well as for the radiointerface between a Relay Node and the E-UTRAN.

The MeNB 202 a is in further communication with an MME 210 of an EPC 211by way of an S1-MME interface. The MeNB 202 a and the SeNB 202 b are incommunication with each other by way of an X2 interface. The X2interface can be accommodated by one or more of a back-haul network or afront-haul network 252. One or more of the MeNB 202 a and the SeNB 202 bcan communicate with the UE 230 via respective Uu protocol interfacesover the air network.

In some embodiments, the system 200 is operated in a synchronous mode.The system 200 can include a timing source 253, such as a precisionsystem clock, and/or a remote timing source, such as a system timesource, a satellite time, e.g., GPS time, or some other reliable timingreference, e.g., the National Institute of Standards and Technology(NIST), WWV coordinated time, and the like. More than one different timesources can be provided in primary and fallback configuration, e.g.,using GPS as a primary synchronization reference and using the NIST WWVas a fall back. The example system also includes a storage element 248.The storage element 248 can be physical storage available at one or moreof the MeNB 202 a and the SeNB 202 b. Alternatively or in addition, thestorage element 248 can include networked storage, e.g., in the form ofcloud storage, or a database.

According to the illustrative example, the MeNB 202 a and the SeNB 202 bcan provided one or more coordinated services to the UE 230. Thecoordinated services can include, without limitation, CoMP, CA and DCfeatures. In some embodiments, a set of possible features is identifiedfor the network 200. The feature set can be stored in a configurationfile, e.g., at the eNB 202 and/or in the storage element 248. Havingestablished that at least some of the features of the feature set dependupon performance of an inter-radio terminal interface, availablefeatures may be restricted to a subset of all possible features based onthe inter-radio terminal interface.

In some embodiments, a performance metric of the X2 interface isdetermined. The performance metric can include one or more of a timereference, a message transit time, a message delay time, a latency, andso forth. The performance metric can include a one way metric, e.g.,from the MeNB 202 a to the SeNB 202 b, from the SeNB 202 b to the MeNB202 a and/or a round trip time between the MeNB 202 a and the SeNB 202b. In some embodiments, the performance parameter of the X2 interface isstored in association with a group of base stations to which theperformance parameter applies, e.g., the MeNB 202 a and the SeNB 202 b.

The performance metric of the X2 interface can be determined by varioustechniques, including a message exchange. For example, an “X2 LatencyDiscovery” message(s) can be added to the 3GPP LTE specification. Withthe new message(s), two cells can automatically communicate and detectthe actual X2 latency, which allows the eNB to dynamically select theoptimal features to maximize the performance and/or efficiency of thenetwork.

In some embodiments, one or more new X2 messages can be defined that arenot currently part of the LTE standards. The new X2 message(s)facilitate detection of a latency associated with a message exchange ofan X2 interface between two cells. It is understood that the new X2message(s) would be added to a future version of the standards, onceadopted.

For example, an X2 latency discovery procedure, including an exchange ofthe new X2 message(s) can be initiated at eNB power-up, periodically,and/or responsive to an event (such as new neighbor addition). It isunderstood that latency may fluctuate for any of various reasons.Accordingly, an eNB can conduct latency testing using an exchange of thenew X2 message(s) several times, to allow for determination of astatistical convergence, a range, etc. An eNB can be configured withintelligence, e.g., within eNB software, to decide when and how often toimplement such latency testing. For example, a frequency for determiningX2 latency can be based on whether some of the LTE-A features will beneeded, e.g., in an on-demand fashion, to avoid any unnecessary extra X2signaling.

FIG. 2B depicts an illustrative embodiment of an X2 message exchange ofan inter eNB latency measurement. A first eNB A 262 a sends a firstmessage 270 to a second eNB B 262 b over an X2 interface 275 between theENBs 262 a, 262 b. In the illustrative example, the first message 270 isan X2 Latency Discovery Request message 270. The X2 Latency DiscoveryRequest message 270 includes an identifier of the first eNB A 262 a,e.g., a global eNB ID. Alternatively or in addition, the X2 LatencyDiscovery Request message 270 includes a served cell Information Element(IE), and a time stamp. The served cell information IE, e.g., accordingto 3GPP TS 36.423 section 9.2.8, includes serving cells PCI (PhysicalCell Identifier), ECGI (E-UTRAN Cell Global Identifier of the neighborcell), TAC (Tracking Area Code), etc. The time stamp can be determinedand otherwise applied to the request message 270 at the time the messageis generated and/or sent to the second eNB B 262 b.

In response to receiving the X2 Latency Discovery Request message 270,the second eNB B 262 b, generates an X2 Latency Discovery Responsemessage 272. The X2 Latency Discovery Response message 272 includes anidentifier of the second eNB B 262 b, e.g., a global eNB ID.Alternatively or in addition, the X2 Latency Discovery Response message272 includes a served cell Information Element (IE), and a time stamp.The served cell information IE, can include one or more of a served cellPCI, ECGI, TAC, etc. The time stamp can be determined and otherwiseapplied to the response message 272 at the time the message 272 isgenerated and/or sent to the first, requesting eNB A 262 a. In at leastsome embodiments, the new X2 messages disclosed herein can be adopted orotherwise incorporated into a future X2 Access Protocol.

In some embodiments, the first node 262 a is a primary serving node andthe second node 262 b is a secondary serving node. The primary andsecondary serving nodes 262 a, 262 b can be arranged to providecoordinated wireless services to UE. Such services can include, withoutlimitation, CoMP, CA and DC. Although the illustrative example includesa request from the primary serving node 262 a to the secondary servingnode 262 b, it is understood that other messaging arrangements can beaccommodated. For example, the secondary serving node 262 b can initiatea request to the primary serving node 262 a that includes a time stamp.The primary serving node can determine a latency by comparing the timestamp to a message receipt time to determine a latency value withoutnecessarily requiring a response message.

Having determined a latency value between the two cells 262 a, 262 b,one or more eNB features can be enabled dynamically, based on thelatency. For example, one or more of CoMP, CA and/or DC can be enabledbased on a latency less than about 1 ms. One or more of CA and/or DC,but not CoMP can be enabled based on a latency greater than about 1 msand less than about 5 ms. A DC, but not CoMP or CA can be enabled basedon a latency greater than about 5 ms, and less than about 50 ms. Othernon-real time features, e.g., load information exchange, can be enabledfor any latency value, e.g., including a latency value greater thanabout 50 ms.

Dynamically enabling eNB features based on detected X2 latency betweentwo cells according to the new X2 message provides a number ofadvantages. By way of non-limiting example, the new X2 latencyrequest/response messages support determination of an accurate andreal-time X2 latency. The X2 latency can be determined automatically,allowing an eNB feature set to be determined and/or otherwise adjustedor updated based on the X2 latency. This allows a mobile network tomaximize feature benefits and improve network performance based onreal-time condition.

By way of example, latency associated with an interface betweenmacro-cells and/or small cells can be accomplished using latencydiscovery messages. Namely, the X2 AP (Application Protocol) can bemodified to include a latency discover request message 240. A 3GPP TS36.423, v13.3.0, entitled “Technical Specification Group Radio AccessNetwork; Evolved Universal Terrestrial Radio Access Network (E-UTRAN);X2 application protocol (X2AP),” providing details of the X2 interface,is incorporated by reference herein in its entirety. The latencydiscovery request message 240 can include one or more of a cellreference, e.g., a global eNB identifier, a served cell information IE(Information Element), and a time stamp.

The X2 AP can be modified further to include a latency discoveryresponse message 242. A latency discovery request message can be sent byone of the eNBs, such as the MeNB 202 a, directed towards the SeNB 202b. The SeNB 202 b, in reply, sends a latency discover response message242. The message 242 can include one or more of a global eNB ID, aserved cell information IE, and a time stamp. The time stamp values canbe determined based on a reference time of the reference time source253. One or both of source and target eNBs of a message exchange cancalculate the X2 latency based on the timestamps.

The latency discovery messages 240, 242 can be performed once, e.g.,during a system configuration. Alternatively or in addition, the latencydiscovery messages can be performed periodically. The periodicity can beregular, e.g., according to a measurement time interval. Alternativelyor in addition, the latency discovery messages 240, 242 can beimplemented according to an event. The event can include one or more ofwireless traffic, back-haul/front-haul traffic, UE identity, networkconfiguration change, time of day, day of week, and so on. In someinstances the latency discovery messages 240, 242 are performed atintervals determined by other factors, such as historical records ofsuch measurements.

If the latency is determined be a relatively stable parameter, thenmeasurements may not need to be performed frequently. Similarly, if thelatency is determined to be relatively unstable, then it themeasurements can be performed more frequently. In some instances, thelatency is determined each time a UE attaches to a particular eNB and/orenters a particular tracking area.

In some embodiments, the measurements of performance metrics, such aslatency, are processed to determine statistics, such as averages,medians, modes, variances, and the like. In some embodiments, thelatency discovery response message includes a one-way transit time. Arecipient eNB/small cell can determine a one-way transit time for an X2interface based on a time stamp in the latency discovery requestreceived over the X2 interface and a message receipt time according tothe time reference 253.

FIG. 3 depicts an illustrative embodiment of an embodiment of a process300 used by the systems of FIGS. 1 and 2. The process includes identifya wireless transceiver group at 302. This can include a pair of basestations/wireless access points, such as the MeNB 202 a and SeNB 202 b(FIG. 2). When more than two access points are involved, the group caninclude more than two access points. In some embodiments, one or morewireless transceiver groups include all possible access points, e.g.,all access points having overlapping coverage, all access points havingoverlapping and/or adjacent coverage, and so forth. In some embodiments,the wireless transceiver group is based on a location of a particular UEand/or a service and/or data transfer requirement for a particular UEand/or particular cell. Thus, if a particular UE is a low data user,and/or a particular macro-cell and/or small cell has no high data rateusers, then the corresponding access points can be excluded from thegroup. Conversely, if a particular UE is a high data user and/or aparticular macro-cell and/or small cell has high data rate users, thenthe corresponding access points can be included within the group.

Latency values between transceiver pairs of transceiver group aredetermined at 304. The latency values can be determined according to anyof the techniques disclosed herein, such as latency request/responsemessages. Alternatively or in addition, latency can be determined frommessages of opportunity, e.g., any message exchanged over an X2interface, and the like. In some instances, the performance parameters,e.g., latency can be measured using other equipment, such as testequipment utilized during a configuration or maintenance service of theradio access network. Such ancillary equipment can remain in place,e.g., periodically testing any of the performance parameters of one ormore of the back-haul and/or front-haul links.

A group of configuration alternatives is identified at 306. Particularconfiguration alternatives can be identified by a network operator,e.g., based on network capabilities, software versions, and the like.This group of configuration alternatives can include all possiblefeatures, without regard to network conditions, latency values and thelike. Alternatively, the group of configuration alternatives can includepredetermined configuration parameters, e.g., according to a servicesubscription, authorization, operator preference, and the like.

The performance parameter, e.g., latency, is compared to a correspondingrequirement for each configuration alternative of the identified groupof configuration alternatives at 308. For example, if the configurationalternatives include CoMP, CA and DC, each having a respective latencyrequirement, the determined latency of the link between wirelesstransceivers of the group is compared to a corresponding latencyrequirement. Such automated determination of authorized configurationsbased on automatic latency measurements allow the system to beconfigured and re-configured, as need be, without necessarily having todetermine whether the eNBs are intra-eNBs or inter-eNBs and/or whetherlow-latency front-haul networks are available, as might be done formanual configurations.

A determination is made at 310 as to whether the comparison issatisfied. Satisfaction can include the latency being such that theconfiguration alternative can be accommodated. In response to afavorable comparison, the corresponding configuration alternative isselected or associated with the wireless transceiver pair at 312, and adetermination is made at 314 as to whether comparisons are necessary forany other configuration alternatives. If so, the process continues fromstep 308. In response to a determination at 310 as that the comparisonis not satisfied, the process continues from step 314.

Having completed the comparisons for each of the configurationalternative of the group to obtain an authorized configuration, one ormore of the authorized configuration alternatives can be applied tomobile services to a UE in communication with the corresponding group ofwireless transceivers. Alternatively or in addition, access to any ofthe non-selected or non-authorized configuration alternatives of thegroup can be restricted or otherwise blocked. It is understood that aslink conditions change, e.g., latency of the X2 interface, are-application of the process 300 can result in a different authorizedconfiguration.

It is also understood that the process can be applied to individualpairs of wireless transceivers of the group of wireless transceivers.For applications involving more than two wireless transceivers,different authorized configurations can be applied according to thecorresponding pair. In some embodiment involving more than two wirelesstransceivers, a common authorized configuration can be applied to theentire group. For example, the authorized configuration can be selectedas the most restrictive, or the least restrictive. With respect tolatency parameters, the authorized configuration can be based on thegreatest latency among the wireless transceiver links of the group oftransceivers.

In general, the process 300 can be applied to any number of coordinatingwireless terminals, e.g., 2, 3 or more, and any group of configurationalternatives related to wireless services to a single UE coordinatedamong multiple wireless terminals. Although the illustrative examplesrefer to selection or authorization being based on latency, it isunderstood that the comparisons can be based on one or more otherperformance parameters, such as delay, signal strength, noise, and soon. In some embodiments, the performance parameters can includecombinations of multiple parameters, such as latency and noise, etc.

The X2 latency between two LTE cells is an important factor fordetermining what features can be supported and whether the feature aresuitable for intra-eNB and/or inter-eNB. Different features havedifferent requirements for X2 latency. For example, CoMP requires themost stringent X2 latency, sub-millisecond, inter-eNB CA requires X2latency less than about 5 ms, and dual connectivity has relaxed X2latency and can use non-ideal backhaul. In terms of the performance,CoMP>inter-eNB CA>dual connectivity, presuming that each of thedifferent features has its corresponding latency requirement met.

It is worth noting that the peer-to-peer latency discovery techniquesdisclosed herein can be distinguished from other latency discoverymechanisms such as TWAMP (Two Way Active Measurement Protocol), e.g.,built upon a client-server (controller/responder) architecture toestimate a backhaul performance (e.g., latency, loss . . . ) between aneNB and a network server. With the peer-to-peer techniques disclosedherein, any eNB can initiate a latency request, which is distinguishablefrom specific client/server concept. The peer to peer latencyfacilitates selection of an optimal eNB feature set.

FIG. 4 depicts an illustrative embodiment of another embodiment ofprocess used by the systems of FIGS. 1 and 2. Latency of an X2 interfacebetween a pair of eNBs is determined at 402. For example, the latencycan be determined for the X2 interface 252 between the MeNB 202 a andthe SeNB 202 b (FIG. 2). The latency can include a time value, e.g.,determined using one or more of the latency discovery request 240 andresponse 242 messages (FIG. 2).

The determined X2 latency is compared to a CoMP latency threshold at404. In some applications, the CoMP latency threshold can be about 1 ms,such that latency measurements less than 1 ms satisfy the CoMP latencythreshold. It is understood that the latency threshold can beestablished at other values, such as 500 microseconds, 100 microseconds,10 microseconds, and/or 5 microseconds, with latency values below thecorresponding threshold satisfying the CoMP requirement.

To the extent that the CoMP latency threshold is satisfied at 408, theCoMP feature is added to an authorized configuration at 410. The processcontinues with the next threshold at 412. To the extent that the CoMPlatency threshold is not satisfied at 408, the process continues withthe next threshold. Namely, the determined X2 latency is compared to aCoMP latency threshold at 404. In some applications, the CoMP latencythreshold can be about 1 ms, such that latency measurements less than 1ms satisfy the CoMP latency threshold. It is understood that the latencythreshold can be established at other values, such as 500 microseconds,100 microseconds, 10 microseconds, and/or 5 microseconds, with latencyvalues below the corresponding threshold satisfying the CoMPrequirement.

To the extent that the CoMP latency threshold is satisfied at 408, theCoMP feature is added to an authorized configuration. In theillustrative scenario the latency value can be divided into severalcategories, according to the features. Latency requirements for some ofthe features can be more restrictive than others. Namely, the latencyrequirements for CoMP are on the order of microseconds, whereas thelatency requirements for inter-eNB are on the order of about 5 ms, andthe latency requirements for dual connectivity are about 50 ms. Byarranging the latency threshold evaluations from most restrictive, e.g.,CoMP, to least restrictive, e.g., DC, it is possible to authorizefeatures having equal or lesser restrictive latency requirements with asingle test. Thus, having established that the CoMP threshold issatisfied at 408, the CoMP feature is authorized at 410, the CA featureis authorized at 416 and the DC feature is authorized at 422.

To the extent that the CoMP latency threshold is not satisfied at 408,the process continues with the next threshold. Namely, compare X2latency to CA latency threshold at 412. In some applications, the CAlatency threshold can be about 5 ms, such that latency measurements lessthan about 5 ms satisfy the CA latency threshold. It is understood thatthe latency threshold can be established at other values, such as 10 ms,1 ms, and so on, with latency values below the corresponding thresholdsatisfying the CA requirement.

To the extent that the CA latency threshold is satisfied at 414, the CAfeature is added to an authorized configuration at 416. Since the DCthreshold is less restrictive, the process also authorizes the DCfeature at 422. To the extent that the CA latency threshold is notsatisfied at 414, the process continues with the next threshold. Namely,the determined X2 latency is compared to a DC latency threshold at 418.In some applications, the DC latency threshold can be about 50 ms, suchthat latency measurements less than about 50 ms satisfy the DC latencythreshold. It is understood that the latency threshold can beestablished at other values, such as 100 ms, 25 ms, and so on, withlatency values below the corresponding threshold satisfying the DCrequirement.

To the extent that the DC latency threshold is satisfied at 420, the DCfeature is added to an authorized configuration at 422. To the extentthat the CA latency threshold is not satisfied at 420, the processcontinues to facilitate operation according to the authorizedconfigurations at 424.

While for purposes of simplicity of explanation, the respectiveprocesses are shown and described as a series of blocks in FIGS. 3 and4, it is to be understood and appreciated that the claimed subjectmatter is not limited by the order of the blocks, as some blocks mayoccur in different orders and/or concurrently with other blocks fromwhat is depicted and described herein. Moreover, not all illustratedblocks may be required to implement the methods described herein.

FIG. 5 depicts an illustrative embodiment of a first communicationsystem 500 for delivering media content. The communication system 500can represent an Internet Protocol Television (IPTV) media system.Communication system 500 can be overlaid or operably coupled with thesystems 100, 200 of FIGS. 1 and/or 2 as another representativeembodiment of communication system 500. For instance, one or moredevices illustrated in the communication system 500 of FIG. 5 identifiesa primary serving cell 517 a and a secondary serving cell 517 b of amobile cellular network 518, wherein the primary serving cell 517 afacilitates coordination of a wireless service to a mobile device 516. Alatency value associated with a message exchange between the primaryserving cell 517 a and the secondary serving cell 517 b via a messaginginterface, X2, is determined. The latency value is compared to latencyrequirements corresponding to a group of mobile service features. Amobile service feature of the group of mobile service features isassociated with the wireless service based on the comparison, whereinthe service includes a coordinated exchange of wireless signals betweenthe primary serving cell 517 a and the mobile device 516 and between thesecondary serving cell 517 b and the mobile device 516 based on themobile service feature of the group of mobile service features.

The IPTV media system can include a super head-end office (SHO) 510 withat least one super headend office server (SHS) 511 which receives mediacontent from satellite and/or terrestrial communication systems. In thepresent context, media content can represent, for example, audiocontent, moving image content such as 2D or 3D videos, video games,virtual reality content, still image content, and combinations thereof.The SHS server 511 can forward packets associated with the media contentto one or more video head-end servers (VHS) 514 via a network of videohead-end offices (VHO) 512 according to a multicast communicationprotocol.

The VHS 514 can distribute multimedia broadcast content via an accessnetwork 518 to commercial and/or residential buildings 502 housing agateway 504 (such as a residential or commercial gateway). The accessnetwork 518 can represent a group of digital subscriber line accessmultiplexers (DSLAMs) located in a central office or a service areainterface that provide broadband services over fiber optical links orcopper twisted pairs 519 to buildings 502. The gateway 504 can usecommunication technology to distribute broadcast signals to mediaprocessors 506 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 508 such as computers or televisionsets managed in some instances by a media controller 507 (such as aninfrared or RF remote controller).

The gateway 504, the media processors 506, and media devices 508 canutilize tethered communication technologies (such as coaxial, powerlineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth®, Zigbee®, or other presentor next generation local or personal area wireless network technologies.By way of these interfaces, unicast communications can also be invokedbetween the media processors 506 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 529 can be used in the mediasystem of FIG. 5. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 500. In thisembodiment, signals transmitted by a satellite 515 that include mediacontent can be received by a satellite dish receiver 531 coupled to thebuilding 502. Modulated signals received by the satellite dish receiver531 can be transferred to the media processors 506 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 508. The media processors 506 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 532 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 533 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system500. In this embodiment, the cable TV system 533 can also provideInternet, telephony, and interactive media services. System 500 enablesvarious types of interactive television and/or services including IPTV,cable and/or satellite.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 530, a portion of which can operate as aweb server for providing web portal services over the ISP network 532 towireline media devices 508 and/or wireless communication devices 516.Delivery of such services to the wireless communication devices 516 canuse one or more of the coordinated service features, e.g., CoMP, CAand/or DC.

Communication system 500 can also provide for all or a portion of thecomputing devices 530 to function as a coordinating controller (hereinreferred to as coordinating controller 530). The coordinating controller530 can use computing and communication technology to perform function562, which can include among other things, the 300, 400 techniquesdescribed by the processes of FIGS. 3 and/or 4. For instance, function562 of the coordinating controller 530 can be similar to the functionsdescribed for the controllers 106 of FIG. 1 and/or the control module206 of FIG. 2, in accordance with the process 300 of FIG. 3 and/or theprocess 400 of FIG. 4. In some embodiments, the coordinating controlleris in communication with one or more of the base stations 517 a, 517 band/or the wireless communications device 516, by way of a mobilenetwork core, e.g., an EPC 570. One or more of the base stations 517 a,517 b, and the wireless communication devices 516 can be provisionedwith software functions 564 and 566, respectively, to utilize theservices of the coordinating controller 530. For instance, functions 564and 566 of the base stations 517 a, 517 b, and the wirelesscommunication devices 516 can be similar to the functions described forthe controllers 106 of FIG. 1 and/or the control module 206 of FIG. 2,in accordance with the process 300 of FIG. 3 and/or the process 400 ofFIG. 4.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of a wireless accessbase station 517 operating according to common wireless access protocolssuch as Global System for Mobile or GSM, Code Division Multiple Accessor CDMA, Time Division Multiple Access or TDMA, Universal MobileTelecommunications or UMTS, World interoperability for Microwave orWiMAX, Software Defined Radio or SDR, Long Term Evolution or LTE, and soon. Other present and next generation wide area wireless access networktechnologies can be used in one or more embodiments of the subjectdisclosure.

FIG. 6 depicts an illustrative embodiment of a web portal 602 of acommunication system 600. Communication system 600 can be overlaid oroperably coupled with systems 100, 200 of FIGS. 1 and/or 2,communication system 500 as another representative embodiment of systems100, 200 of FIGS. 1 and/or 2, communication system 500. The web portal602 can be used for managing services of systems 100, 200 of FIGS. 1and/or 2 and communication system 500. A web page of the web portal 602can be accessed by a Uniform Resource Locator (URL) with an Internetbrowser using an Internet-capable communication device such as thosedescribed in FIGS. 1 and/or 2 and FIG. 5. The web portal 602 can beconfigured, for example, to access a media processor 506 and servicesmanaged thereby such as a Digital Video Recorder (DVR), a Video onDemand (VoD) catalog, an Electronic Programming Guide (EPG), or apersonal catalog (such as personal videos, pictures, audio recordings,etc.) stored at the media processor 506. The web portal 602 can also beused for provisioning IMS services described earlier, provisioningInternet services, provisioning cellular phone services, and so on.

The web portal 602 can further be utilized to manage and provisionsoftware applications 562-566, to adapt these applications as may bedesired by subscribers and/or service providers of systems 100, 200 ofFIGS. 1 and/or 2, and communication system 500. For instance, users ofthe services provided by the coordinating controller, the base stations517 a, 517 b and/or the wireless communication device 516, can log intotheir on-line accounts and provision the servers 110 or server 430 withparameters related to the coordinated wireless services. For example,such parameters can include, without limitation, a group of mobilefeatures, e.g., CoMP, CA and/or DC. Alternative or in addition, suchparameters can include performance parameters for links between wirelessaccess points, such as latency, associated with each mobile feature ofthe group. Other features can include authorizations, user preferences,levels of subscription, and the like. Service providers can log onto anadministrator account to provision, monitor and/or maintain the systems100, 200 of FIGS. 1 and/or 2 or server 530.

FIG. 7 depicts an illustrative embodiment of a communication device 700.Communication device 700 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and/or 2, andFIG. 4-5 and can be configured to perform portions of the processes 300,300 of FIGS. 3 and/or 4.

Communication device 700 can comprise a wireline and/or wirelesstransceiver 702 (herein transceiver 702), a user interface (UI) 704, apower supply 714, a location receiver 716, a motion sensor 718, anorientation sensor 720, and a controller 706 for managing operationsthereof. The transceiver 702 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 702 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 704 can include a depressible or touch-sensitive keypad 708 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device700. The keypad 708 can be an integral part of a housing assembly of thecommunication device 700 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 708 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 704 can further include a display710 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 700. In anembodiment where the display 710 is touch-sensitive, a portion or all ofthe keypad 708 can be presented by way of the display 710 withnavigation features.

The display 710 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 700 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 710 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 710 can be an integral part of thehousing assembly of the communication device 700 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 704 can also include an audio system 712 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 712 can further include amicrophone for receiving audible signals of an end user. The audiosystem 712 can also be used for voice recognition applications. The UI704 can further include an image sensor 713 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 714 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 700 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 716 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 700 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 718can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 700 in three-dimensional space. Theorientation sensor 720 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device700 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 700 can use the transceiver 702 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 706 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 700.

Other components not shown in FIG. 7 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 700 can include a reset button (not shown). The reset button canbe used to reset the controller 706 of the communication device 700. Inyet another embodiment, the communication device 700 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 700 to force thecommunication device 700 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 700 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 700 as described herein can operate with moreor less of the circuit components shown in FIG. 7. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 700 can be adapted to perform the functions ofdevices 130, 230 of FIGS. 1 and/or 2, the media processor 406, the mediadevices 408, or the portable communication devices 416 of FIG. 4, aswell as the IMS CDs 501-502 and PSTN CDs 503-505 of FIG. 5. It will beappreciated that the communication device 700 can also represent otherdevices that can operate in systems 100, 200 of FIGS. 1 and/or 2,communication systems 400-500 of FIGS. 4-5 such as a gaming console anda media player. In addition, the controller 706 can be adapted invarious embodiments to perform the functions 562-566, respectively.

Different LTE-A features have different requirements on latency betweentwo cells. Heterogeneous network, “HetNet,” deployments can includeconfigurations with different latencies. With the rapid growth of HetNetand the transition to 5G, dynamically configuring a RAN (Radio AccessNetwork) feature set based on performance, such as latency, between twocells can improve HetNet performance, enable operation automation,promote efficiency, and save operation cost.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, the techniques disclosed herein canbe integrated with SON (Self Optimizing or Self Organizing Networks) toprovide network automation and optimization. It is also understood thatthe various improvements disclosed herein support automation of networkoperations, save costs and support future features, e.g., 5G and/orEnable HetNet scalability . . . Other embodiments can be used in thesubject disclosure.

SON includes automation technologies that facilitate planning,configuration, management, optimization and/or healing of mobile radioaccess networks. Existing SON functionality and behavior have beenadopted and otherwise specified by organizations such as 3GPP and theNGMN (Next Generation Mobile Networks). It is understood that such SONfunctionality can be enhanced and/or extended to include one or more ofmobile network configuration, mobile network optimization and or mobilenetwork healing based on X2 latency values obtained using the new X2latency discovery messages.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 8 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the coordinating controller 106, 206, 530, thewireless access terminal 102, 114, 116, 118, 202, 517. In someembodiments, the machine may be connected (e.g., using a network 826) toother machines. In a networked deployment, the machine may operate inthe capacity of a server or a client user machine in a server-clientuser network environment, or as a peer machine in a peer-to-peer (ordistributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 800 may include a processor (or controller) 802(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 804 and a static memory 806, whichcommunicate with each other via a bus 808. The computer system 800 mayfurther include a display unit 810 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 800may include an input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), a disk drive unit 816, a signal generationdevice 818 (e.g., a speaker or remote control) and a network interfacedevice 820. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units810 controlled by two or more computer systems 800. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 810, while the remainingportion is presented in a second of the display units 810.

The disk drive unit 816 may include a tangible computer-readable storagemedium 822 on which is stored one or more sets of instructions (e.g.,software 824) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 824 may also reside, completely or at least partially,within the main memory 804, the static memory 806, and/or within theprocessor 802 during execution thereof by the computer system 800. Themain memory 804 and the processor 802 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. Distributedprocessing environments can include multiple processors in a singlemachine, single processors in multiple machines, and/or multipleprocessors in multiple machines. It is further noted that a computingdevice such as a processor, a controller, a state machine or othersuitable device for executing instructions to perform operations ormethods may perform such operations directly or indirectly by way of oneor more intermediate devices directed by the computing device.

While the tangible computer-readable storage medium 822 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, Zigbee®), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 800. In one or more embodiments, information regardinguse of services can be generated including services being accessed,media consumption history, user preferences, and so forth. Thisinformation can be obtained by various methods including user input,detecting types of communications (e.g., video content vs. audiocontent), analysis of content streams, and so forth. The generating,obtaining and/or monitoring of this information can be responsive to anauthorization provided by the user.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A method, comprising: identifying, by aprocessing system including a processor, a primary serving cell and asecondary serving cell of a mobile cellular network; obtaining, by theprocessing system, a comparison between a plurality of latencyrequirements associated with a plurality of mobile features and alatency value associated with a message exchange, via a messaginginterface, between a primary serving cell and a secondary serving cell;and selecting, based on the comparison, by the processing system, amobile feature of the plurality of mobile features, wherein the mobilefeature comprises a coordinated exchange of wireless signals between theprimary serving cell and a mobile device and between the secondaryserving cell and the mobile device.
 2. The method of claim 1, whereinthe primary serving cell facilitates one of attachment of a mobiledevice to a mobile cellular network, re-attachment of the mobile deviceto the mobile cellular network, or mobility of the mobile device betweenthe primary serving cell and another cell of the mobile cellularnetwork.
 3. The method of claim 1, wherein the primary serving cell isassociated with a first base station of a mobile cellular network andthe secondary serving cell is associated with a second base station ofthe mobile cellular network.
 4. The method of claim 3, wherein thelatency value, associated with a message exchange via a messaginginterface between the primary serving cell and the secondary servingcell, is determined by exchanging an X2 latency message between thefirst base station and the second base station using an X2 applicationprotocol of the messaging interface that includes the X2 latencymessage.
 5. The method of claim 1, further comprising determining, bythe processing system, a demand for the mobile feature of the pluralityof mobile features, wherein selection of the mobile feature isassociated with the demand that is determined.
 6. The method of claim 1,wherein the plurality of mobile features includes coherent joint radiofrequency transmissions from the primary serving cell and the secondaryserving cell to the mobile device, an aggregation of radio frequencycarriers of the primary serving cell and the secondary serving cell, adual connectivity between the primary serving cell, the secondaryserving cell and the mobile device, or any combination thereof.
 7. Themethod of claim 6, wherein the aggregation of radio frequency carrierscomprises a 3rd Generation Partnership Protocol, Long Term Evolutioncarrier aggregation.
 8. The method of claim 6, wherein the dualconnectivity comprises a 3rd Generation Partnership Protocol, Long TermEvolution coordinated multipoint transmissions.
 9. A system, comprising:a processing system including a processor; and a memory that storesexecutable instructions that, when executed by the processing system,facilitate performance of operations, the operations comprising:obtaining a comparison between a plurality of latency requirementsassociated with a plurality of mobile features and a latency valueassociated with a message exchange, via a messaging interface, between aprimary serving cell associated with a first base station of a mobilecellular network and a secondary serving cell associated with a secondbase station of the mobile cellular network; and selecting, based on thecomparison, a mobile feature of the plurality of mobile features,wherein the mobile feature comprises a coordinated exchange of wirelesssignals between the primary serving cell and a mobile device and betweenthe secondary serving cell and the mobile device.
 10. The system ofclaim 9, wherein the operations further comprise identifying the primaryserving cell and the secondary serving cell of the mobile cellularnetwork.
 11. The system of claim 9, wherein the primary serving cellfacilitates one of attachment of a mobile device to a mobile cellularnetwork, re-attachment of the mobile device to the mobile cellularnetwork, or mobility of the mobile device between the primary servingcell and another cell of the mobile cellular network.
 12. The system ofclaim 9, wherein the latency value, associated with a message exchangevia a messaging interface between the primary serving cell and thesecondary serving cell, is determined by exchanging an X2 latencymessage between the first base station and the second base station usingan X2 application protocol of the messaging interface that includes theX2 latency message.
 13. The system of claim 9, wherein the operationsfurther comprise determining a demand for the mobile feature of theplurality of mobile features, wherein selection of the mobile feature isassociated with the demand that is determined.
 14. The system of claim9, wherein the plurality of mobile features includes coherent jointradio frequency transmissions from the primary serving cell and thesecondary serving cell to the mobile device, an aggregation of radiofrequency carriers of the primary serving cell and the secondary servingcell, a dual connectivity between the primary serving cell, thesecondary serving cell and the mobile device, or any combinationthereof.
 15. The system of claim 14, wherein the aggregation of radiofrequency carriers comprises a 3rd Generation Partnership Protocol, LongTerm Evolution carrier aggregation.
 16. The system of claim 14, whereinthe dual connectivity comprises a 3rd Generation Partnership Protocol,Long Term Evolution coordinated multipoint transmissions.
 17. Amachine-readable storage medium, comprising executable instructionsthat, when executed by a processing system including a processor,facilitate performance of operations, comprising: accessing, by theprocessing system, a comparison between a plurality of latencyrequirements associated with a plurality of mobile features and alatency value associated with a message exchange, via a messaginginterface, between a primary serving cell and a secondary serving cell;and determining, based on the comparison, by the processing system, amobile feature of the plurality of mobile features, wherein the mobilefeature comprises a coordinated exchange of wireless signals between theprimary serving cell and a mobile device and between the secondaryserving cell and the mobile device.
 18. The machine-readable storagemedium of claim 17, wherein the mobile feature of the plurality ofmobile features is determined according to a demand for the mobilefeature.
 19. The machine-readable storage medium of claim 17, whereinthe latency value, associated with a message exchange via a messaginginterface between the primary serving cell and the secondary servingcell, is determined by exchanging an X2 latency message between a firstbase station and a second base station using an X2 application protocolof the messaging interface that includes the X2 latency message.
 20. Themachine-readable storage medium of claim 17, wherein the latency valuecomprises a time delay.